System and Method for Swapping of Tangible and Intangible Items

ABSTRACT

A first user, second user, and third user are registered. Names of a first, second, and third item are stored a website for the first, second, and third users. The items can be tangible items or intangible items. The first user requests the second item. A first credit is removed from the first user and a second credit is stored for the second user when the first user receives the second item. The second user requests the third item. The second credit is removed from the second user and a third credit is stored for the third user when the second user receives the third item. The first credit, the second credit, and the third credit each represents a right to request a future swappable intangible item for the equivalent value of at least one previously swapped intangible item.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 14/027,296, filed Sep. 16, 2013, now U.S. Pat. No. 8,751,325, issued Jun. 10, 2014, which is a continuation of U.S. patent application Ser. No. 13/355,554, filed Jan. 22, 2012, now U.S. Pat. No. 8,538,859, issued Sep. 17, 2013, which is a continuation-in-part application of U.S. patent application Ser. No. 12/978,485, filed Dec. 24, 2010, which is a continuation application of U.S. patent application Ser. No. 11/230,910, filed Sep. 20, 2005, now U.S. Pat. No. 7,877,315, issued Jan. 25, 2011. U.S. patent application Ser. No. 11/230,910 claims the benefit of U.S. Provisional Patent Application No. 60/611,632, filed Sep. 21, 2004. U.S. patent application Ser. No. 13/355,554 claims the benefit of U.S. Provisional Patent Application No. 61/435,247, filed Jan. 21, 2011 and U.S. Provisional Patent Application No. 61/445,600, filed Feb. 23, 2011. All of the above mentioned applications are incorporated by reference herein in their entireties.

BACKGROUND OF THE INVENTION

Tangible and intangible items have long been swapped or exchanged. For example, in the past a farmer might provide a doctor with a dozen eggs (tangible item) in return for the service (intangible item) of treating a family member. Exchanges of tangible and intangible items, however, were generally difficult. Traditionally, they required, at least, a negotiation and a valuation of the items. Also, the introduction of and wide use of a standard, liquid, and trusted coin or paper currency made it much less appealing to exchange tangible and intangible items.

Recent advances in technology and communications have made exchanging all types of items easier, including tangible and intangible items. Further, other technological advancements have produced tangible and intangible items that are like-kind property. Like-kind property is property that is similar in nature or character, and generally used for the same purpose. Exchanges of like-kind property can be more advantageous than exchanges for currency. For example, in the United States, exchanges of some like-kind property are tax free.

An example of like-kind property that is now available as both a tangible item and an intangible item is copyrighted intellectual property. Copyrighted intellectual property can include, but is not limited to, songs, software, games, movies, or novels. Copyrighted intellectual property is now sold on both tangible and intangible media. Tangible media can include, but is not limited to, compact discs (CDs), digital video disks (DVDs), or books. Intangible media can include digital files and these digital files can include, but are not limited to, MP3 files or e-books.

For a long time, owners of copyrighted intellectual property on tangible media have been allowed to exchange these tangible items. Recently, however, content providers of copyrighted intellectual property have also allowed users to lend or exchange their intangible media to other users. For example, some e-book providers have allowed a user to lend an e-book to another user for 14 days.

As more and more like-kind tangible and intangible items become available for swapping, systems and methods are needed to manage the lending and swapping of tangible and intangible items.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting the swapping service environment.

FIG. 2 is a flow diagram generally showing an operation of the swapping service.

FIG. 3 is a diagram showing the main functions of the swapping service.

FIG. 4 is a flow chart showing the registration function of the swapping service.

FIG. 5 is a flow chart showing the procedure for listing an item with the swapping service.

FIG. 6 is an exemplary display of a page useful for listing an item with the service.

FIG. 7 is an exemplary display of a page useful for viewing items listed with the service by a user.j

FIG. 8 is a flow chart of a procedure for assisting a user to ship an item requested by another user.

FIG. 9 is a flow chart of a procedure for requesting a particular item for shipment.

FIGS. 10A, 10B and 10C are portions of an exemplary web page useful for searching for a particular item listed with the service.

FIG. 10D illustrates an example of a screen that may be displayed after a member has requested or ordered an item from another member.

FIG. 11 is a flow chart of a procedure for purchasing credits with the service.

FIG. 12 is a flow chart of a procedure for shipping an item to a person who is not registered with the service.

FIG. 13 is a flow chart of a procedure for delivering an item to a drop box for delivery to a user, rather than shipment through the mail.

FIG. 14 is a diagram showing an example of a pre-formatted mailing wrapper.

FIG. 15 is an image of the mailing wrapper placed around a book ready for mailing.

FIGS. 16-19 depict exemplary screens associated with a Wish List feature.

FIG. 20 depicts an exemplary screen for searching a Global Wish List associated with all members to the service.

FIGS. 21-23 depict exemplary screens associated with the Save Search feature.

FIG. 24 illustrates an exemplary screen associated with the Daily Digest feature.

FIGS. 25 and 26 illustrate exemplary screens associated with the Buddy List feature.

FIGS. 27-29 illustrate exemplary screens for the Public Profiles feature.

FIG. 30 is a block diagram that illustrates a computer system, upon which embodiments of the present teachings may be implemented.

FIG. 31 is a schematic diagram of a system for managing swaps of tangible and intangible items that shows the registration of a first tangible item, in accordance with various embodiments.

FIG. 32 is a schematic diagram of a system for managing swaps of tangible and intangible items that shows the registration of a second intangible item, in accordance with various embodiments.

FIG. 33 is a schematic diagram of a system for managing swaps of tangible and intangible items that shows the registration of a third tangible item, in accordance with various embodiments.

FIG. 34 is a schematic diagram of a system for managing swaps of tangible and intangible items that shows a first request for second intangible item, in accordance with various embodiments.

FIG. 35 is a schematic diagram of a system for managing swaps of tangible and intangible items that shows a first message sent to second user device, in accordance with various embodiments.

FIG. 36 is a schematic diagram of a system for managing swaps of tangible and intangible items that shows a second message sent from first user device, in accordance with various embodiments.

FIG. 37 is a schematic diagram of a system for managing swaps of tangible and intangible items that shows a second request for third tangible item, in accordance with various embodiments.

FIG. 38 is a schematic diagram of a system for managing swaps of tangible and intangible items that shows a third message sent to third user device, in accordance with various embodiments.

FIG. 39 is a schematic diagram of a system for managing swaps of tangible and intangible items that shows a forth message sent from second user device, in accordance with various embodiments.

FIG. 40 is a flowchart showing a method for managing swaps of tangible and intangible items, in accordance with various embodiments.

FIG. 41 is a schematic diagram of a system that includes one or more distinct software modules that perform a method for managing swaps of tangible and intangible items, in accordance with various embodiments.

DETAILED DESCRIPTION

Referring first to FIGS. 1 and 2, a swapping service is depicted that may be used to swap items of any type between user's that have registered with the swapping service. Examples of items that may be swapped with the swapping service described herein are paperback books, hardback books, music CDs, movie/video DVDs, etc. Generally, this system is useful to facilitate swapping of any item where the item value is less than a subscription or membership fee charged to members. However, even this value limitation may not be necessary if the swapping transaction is secured by a credit instrument, such as a credit card. Some basic concepts of the swapping service and system are described. A swapping service 100 manages trades or exchanges of items between users or subscribers (also called members) 200(1) to 200(N) to the service. The service collects a membership or subscription fee from members in exchange for providing the service that enables members to swap items. The fee may be collected on an annual basis, for example, or a monthly basis. Unlike existing trading systems, the items generally are not inventoried by the swapping service but rather stay in the possession of the respective users. Thus, the inventory is kept in the possession and control of the individual members of the club, removing the burden of the service to store inventory. Each user registers with the swapping service 100 and receives some initial credits for requesting items from other users. A credit is used and exhausted by a member when he/she requests an item from another user. On the other hand, a user that delivers an item to a requesting user earns a credit for doing so. Users may list their items available for trading/swapping with the service so that other users may find and request them. For example, user 1 has item A and user 1 provides information to the system that identifies item A. Examples of this identifying information are described hereinafter. Similarly, user 2 has item B and lists it with the service, and user 3 has items C, D and E and lists them with the service.

According to one aspect of the swapping service, when one user desires an item of another user, it requests the service to have the item sent to the requesting user. For example, if user 2 requests item A from user 1, user 1 would receive a notification, such as an email, that contains a printable shipping wrapper or label that includes the mailing address of user 2, and user 1 uses the mailing wrapper to mail or send item A to user 2. User 2 need not ever be made away of the identity of user 1. User 1 earns a credit when he/she ships item A to user 2. Alternatively, user 2 may request that item A be shipped to a third party who is not a user with the system, such as in the case where user 2 desires to send item A as a gift to a third party. In either case, the sender of the item bears the cost of shipping the item, but receives a credit with the service upon receipt of the item by the other party. There are no transactions charges to the sending member or receiving member for use of the service. The system issues a credit to the shipping member (e.g., user 1) when the receiving member or third party logs into the system and confirms receipt of the item. Alternatively, a particular technique described hereinafter may be employed to automatically determine when a shipment was successful received without requiring a party to log into the system and confirm that event.

According to another aspect of the swapping service, a technique is provided for managing credits (used to obtain an item from another user) is described herein, and for initializing each new user with credits to maintain the continuity of the swapping service. Shipment of one item by a first member to a second member results in the first member receiving credit, such as a single credit, per item shipped. Members are free to make an unlimited number of transactions per a given subscription term, subject to the number of credits each member has available.

The service may be hosted on a server computer connected to the Internet. Data for operating the service is stored in an electronic database, either local to the server computer or remote.

FIG. 3 illustrates some of the high level functions of the swapping service performed by the swap server 3.0, comprising Registration 3.1, “List a Book” 3.2, “Remove a Book” 3.3, “Ship a Book” 3.4, “Leave Review” 3.5, “Tell a Friend” 3.6, “Testimonial” 3.7, “Request a Book” 3.8, “Topic Discussion Forum” 3.9, “Buy Credits” 3.10, “Pay Membership Fee” 3.11, “Feedback” 3.12 and “Ship Book Outside System” 3.13. Data from users is obtained through forms presented through a user interface common to Internet web sites. Other features of the system that are, for simplicity, not shown in FIG. 3, are described hereinafter as well.

FIG. 4 illustrates the Registration service. In step 3.1 a, a main registration form is presented to a user into which a user enters data sufficient to register the user with the system, including home address, email address and other relevant data. The user data is validated as being sufficient in step 3.1 b, and then in step 3.1 c, a terms-of-use statement is presented to the user that the user must click to accept in step 3.1 d in order to proceed. In step 3.1 e, the user is presented with a page that asks whether the user lives in a certain geographic area (such as a subdivision), for reasons explained hereinafter. If so, then in step 3.1 g, the user is asked to enter the name of the defined geographic area. Other user data may be obtained in step 3.1 h, and then in step 3.11, the user is asked to submit payment for the membership or subscription fee. This could also occur in reverse order as well.

FIG. 5 illustrates the List a Book function 3.2, invoked when a user desires to list an item to be made available for trade, where the item to be listed is, for example a book. Most books have unique identifiers called an ISBN, which is a standard numbering system for books according to the International Standard Book Number Agency. In step 3.2 a, the user is prompted whether the book has an ISBN. If so, the procedure continues to the left side of FIG. 5. In step 3.2 a 2, the user enters the ISBN for the book and in step 3.2 a 3, the system determines if it is a valid ISBN. If so, then in step 3.a 4, a page is displayed to the user confirming the information for that ISBN so that the user can indicate whether it is the correct book in step 3.2 a 5. Next, in step 3.2 a 6, the system determines whether the corresponding book has a set genre associated with it. If so, the system stores that genre information, and if not, in step 3.2 a 7, the system displays a page asking the user to enter genre information for the book. Then, in step 3.2 a 8, the user is asks whether he/she wants to enter additional books, and if so, the process continues from step 3.2 a. If not, the process continues to a page that displays a list of the books that user has listed, called the My Bookshelf page/function.

When, in step 3.2 a, it arises that the book does not have an ISBN, then the system presents a page that asks the user to enter the title, author, pages, and dimensions (width, height and thickness) of the book in step 3.2 a 1, and then the process continues to step 3.2 a 5, described above. The system uses the item information to calculate the postage amount required by the member who is requested to send the item to its destination. For example, it is possible that some items of like kind have different dimensions (e.g., different number and/or size of pages of a book, or multiple volume CD or DVD works, etc.) The item may be sent by conventional postal services, or by other shipping services such as UPS or Federal Express, in which case depending on the type of delivery service, the corresponding approximate shipping fee is computed by the swapping service. In addition, the system will automatically find the U.S. or other (non U.S.) postal zip code (plus 4) digits and include that information, as well as the U.S. routing barcode symbol in the print data for the book wrapper. The system may also include a tracking number to allow the requesting member and sending member track the item during shipment. This feature and an automatic delivery confirmation feature are described hereinafter. The system may retrieve the book information based on an ISBN input by a member. One way to do this is to use a dedicated ISBN database, which is commercially available. FIG. 6 illustrates an example of what a List a Book web page may look like, and FIG. 7 illustrates an example of the My Bookshelf page, where three books have been listed by a particular user.

The system builds a database of items available for swapping on a first-in first-out (FIFO) basis. As a result, if more than one member lists the same item, the member who listed that item first in time will be offered an opportunity to ship that item to the requesting member. Thus, the member who is first to list is the first to ship and therefore the first to receive a credit. This encourages members to promptly list any items that they have and also makes it fair to other members who list their items promptly by awarding them the chance to earn the credit before other members. This FIFO policy may be further refined and performed on a geographical-basis (regional, state or city). For example, the system may examine the database to identify the member located in a particular region (East Coast, West Coast, Midwest, etc.) that first listed the item. This can help achieve faster delivery times.

There is a “Remove Book” icon that can be selected from the My Bookshelf page as shown in FIG. 7. The Remove a Book function 3.3 presents a page with details of the book that a user has selected for deletion. After removing a book, the user is returned to the My Bookshelf page.

FIG. 8 illustrates the flow chart for the Ship Book function 3.4. In step 3.4 a, the system sends an email message to a first user having in his/her possession an item requested by a second user. The email may ask the first user if he/she can mail the item (e.g., book) in the next X number of hours. For example, in one embodiment, the email message sent by the system to the first user may contain an embedded link that, when selected, logs the first user into the service's web site without the first user having to enter a user name and password. More specifically, the system may include in the embedded link in the email message a predetermined alphanumeric security code that, such that when the link is selected, the system can retrieve that alphanumeric security code to verify its authenticity and allow the first user into the service's web site without user name/password verification. In any even, if the user indicates, once on the web site, that he she can deliver the item, the process then proceeds to the right side of FIG. 8 where the system determines if the first user lives or resides local (short driving distance) to the second user. If so, then the first user can decide to mail the item to the second user or drop the item in a drop box according to a Drop Box function 5.0 described hereinafter.

If the users are not local to each other or the shipping user wishes to mail the item, then in step 3.2 b 1 a, the first user would click “yes” in a link in the email that presents the user with a mailing wrapper (in the form of a PDF or other suitable document format) with the second user's mailing address already printed on it. In step 3.2 b 1 b, the first user prints the document and wraps the mailing wrapper around the item, applies postage, and mails the item to the second user. It is important to note that the mailing wrapper document is formatted such that it can be printed by a standard computer printer using standard size paper, yet when used as instructed, essentially serves as a pre-addressed mailing envelope.

If, in step 3.2 b, the user with the requested item indicates that he/she cannot mail the item within the specified period of time, then in step 3.2 b 2 a, the system searches to see if another user has listed that same item. If so, then the process proceeds to step 3.4 a where that other user with the same item is prompted as indicated in FIG. 8. If in step 3.2 b 2 b the system determines there is no other copy of the book available (other than the first member determine to have listed the book, but can't ship it within the next X hours, no other member has listed it), then the system in step 3.2 b 2 c sends another email to the first member in possession of the requested item to inquire if he/she can ship the book with a longer period of time, e.g., 5 days. If so, then the process continues to the right side of FIG. 8 where the user is either prompted to drop the item in a drop box, or is supplied with mailing wrapper data for print. An example of a mailing wrapper is shown in FIGS. 14 and 15 described hereinafter, together with uses and advantages of the mailing wrapper. If that first member who has the listed item cannot ship it even with the longer period of time, e.g., 5 days, then the process terminates the ship book function, and informs the member requesting that item that it is not available.

To summarize the procedure of FIG. 8, if a first member determined to have listed a requested item cannot ship the book within a first relatively short period of time, the system will determine if there is another member who has listed that book and can ship it within the second relatively short period of time. If no other member has listed the book or if that other member cannot ship it within that period of time, the system will go back to the first member and determine whether he/she can ship it within a longer period of time. This process may be performed in any order, the main concept being that the system searches for the member that has listed the requested item and can ship it the soonest. This will be the member that will first get the opportunity to earn a credit by shipping the item to a requested user. The system will look for another member who has listed the same item in the event the first member contacted cannot deliver the item (within some prescribed period of time), and if no other member has listed the same item, the system will terminate the order.

An important aspect of the Ship a Book Function is that the system includes the mailing address of the party to receive the item (either another member or a person not a member to the service) without requiring that the mailing member know the recipient party to receive the item, or to have consummated a transaction with the requesting member. The service merely finds the member who has a particular item requested by a requesting member, and provides the mailing address needed by the member with that item to mail the item either to the requesting member or another party designated by the requesting member. To reiterate, the member with the item, the member requesting the item, and the party who is to receive the item need have no contact with each other (and therefore no exchange of personal or other information) in order to consummate the transaction, except to the “mail to” address. The service handles all of this in the background.

The Leave Book Review function 3.5 allows a user to leave a descriptive review of a particular item (e.g., book) for other users to read in helping other users to select a particular book through the swapping service. In addition, this function may permit a user to enter a rating of the book on a scale of 1-10.

The Tell a Friend function 3.6 permits a user to enter email addresses of other persons that may be interested in the swapping service. The swapping service sends an email message to those persons, together with an introduction to the service.

The Testimonials function 3.7 presents a page to a user and prompts a user to comment on the swapping service itself, with permission to use that comment as a publishable testimonial about the service for marketing purposes.

With reference to FIGS. 9 and 10A, 10B and 10C, the Request a Book function 3.8 will be described. In step 3.8 a, a user is presented with a page, such as the one shown in FIG. 9, which allows a user to search for a particular item, e.g., book in several ways, including title, author, ISBN, or subject matter category, publisher, publish date, key words in book description, large print, audio books, hardcover vs. paperback, and genre. In step 3.8 b, the results of the search are displayed on a page to the user. In step 3.8 c, the user is asked if the book(s) listed are the ones he/she is searching for. If so, then in step 3.8 d, the user is asked if the item should be shipped to the user's address, or an alternate address. If it is to be shipped to an alternate address, a page is presented in step 3.8 e that asks the user to enter the address of where the book is to be shipped. If it is to be shipped to the user's address, then in step 3.8 f, the system determines whether that particular book is available (from the other user who has it) in the requesting user's community. If so, then, the process proceeds to the Drop Box function 5.0. Otherwise, the process proceeds to step 3.8 g in which the system retrieves the user's address and then in step 3.8 h the system displays a page that indicates to the requesting user when they should expect to receive the book. At this point, the requesting user essentially gets confirmation that the book he/she requested will be delivered, and particularly when he/she can expect to receive delivery of it. The user who has that book will be contacted by the system according to the process described above in connection with FIG. 8. When, in step 3.8 e, a user enters a shipping address for a person who is not a member, subscriber or user with the swapping service, then the process continues to the Ship Book Outside System function 3.12, described hereinafter in conjunction with FIG. 12.

When a party (member or non-member) receives an item shipped from a member, text printed on the shipping wrapper instructs that person to log onto the web site for the service to confirm their receipt of that item. FIG. 10D illustrates an example of a screen that may be displayed after a member has requested or ordered an item from another member. This screen may be displayed each time the ordering member logs into the system, and once the item is received, that party may click the button “Was the Book Received” or may click on this button in the event the book is not received by the estimated delivery date. If the receiving party is another member with the service, then that member may also be prompted to automatically repost that item with the service after a user-selectable period of time, or to not automatically repost that item.

Another feature that the swapping service may provide is to allow a member to enter information about an item that is not currently available. The system will monitor new items listed with the service, and when it becomes available, the system may generate an email that is sent to the member advising of the availability of the item, or may display a notice to the member when the member logs into the system.

The Topics Discussion Form function 3.9 allows users to select a particular topic, or enter a new topic not already listed, to enter an on-line discussion or chat about a particular topic, with other users.

The Buy Credits function 3.10 is depicted in FIG. 11. This function may be invoked by a user when the user has exhausted his/her credits by requesting books from another user. A credit initialization scheme is described hereinafter. In step 3.10 a, a page is presented to a user that states the prices for credits and allowing the user to choose how many credits to buy. In step 3.10 b, a page is displayed that confirms to the user the amount of credits chosen for purchase, and if the user confirms this, then in step 3.10 c, payment data is sent to a payment processor for processing. At the completion of this function, the user may be returned to the My Bookshelf page.

FIG. 12 illustrates the Ship Book Outside System function 3.12. It is invoked when a user directs the system to ship a book to an address for a person who is not a user or member of the service. In step 3.12 a, a page is displayed that asks the user to enter the address for shipment of the book. In step 3.12 b, the user is prompted to select whether the item should be shipped accompanied by a personal message or with a standard message. If the user selects for a personal message to be used in step 3.12 c, then in step 3.12 d, a page is presented asking the user to enter the personal message that is to be printed on the back side of the mailing wrapper. In step 3.12 e, a page is presented that shows/previews the personal message for the user. And in step 3.12 f, the user confirms the message and it is stored and used for entering onto the mailing wrapper. When, in step 3.12 c, the user selects a standard message, then in step 3.12 g, a page is presented that states when the user can be expect the item to be delivered.

FIG. 13 illustrates the Drop Box function 5.0. This function is invoked when a user decides that a book can be delivered to him/her locally without use of the mail by depositing the book in a “drop box” that has been set up in a locale that is convenient to the user requesting the item and the user delivering the item. There may be many drop boxes set up in various towns and cities that are associated with the swapping service. The drop box may be equipped with a coded lock or safe and the code is provided only to members that require access to it for depositing an item or retrieving an item. For purposes of this discussion, user 1 is user that has the item and will make delivery of it to the drop box, and user 2 is the user that is requesting the item, and has also requested that it be delivered via the drop box, rather than mail. In step 5.01, the swapping service sends an email to user 1 that contains the printable mailing wrapper on which the name of user 2 is included. In step 5.02, user 1 takes the item, now wrapped in the mailing wrapper, to the local drop box and leaves it in the drop box. In step 5.03, user 1 logs into the system again and makes an indication with the system that the book has been dropped off at the drop box. In step 5.04, the system sends an email or other notification (while user 2 has an open session with the system) indicating that the book has been dropped off and is available. In step 5.05, user 2 picks up the book from the drop box. In step 5.06, user 6 logs into the system and notifies the system that user 2 received and has possession of the book. Then, in step 5.07, the system grants the credit to user 1 for making good on the delivery of the book.

As an alternative to a drop box, a truck or van may drive around various communities and stop at a particular location to allow members to drop off items and pick up other items. This would allow for verification by the person handling the truck or van to be sure only the authorized members can retrieve an item. The truck or van would then move to a location in another community and do the same. The schedule stops of the van would be made known to the appropriate member to allow them to conduct their transactions.

Still a further alternative is a PO Box type system where each member has their own key to their box. A vendor would sort the incoming items and place them for pick up in the boxes, much like the post office, but on site within a neighborhood.

Thus, as described above the drop box alternative may take the form of a box manned by a person who can authorize delivery of an item to the proper member or non-member, or an unmanned box.

Turning to FIG. 14, an example of a mailing wrapper document is shown. This document is created by the swap server 3.0 and sent by email or downloaded to a user in a convenient generic document format, such as the well known portable document format (PDF). It is easily printed by a user's printer. The document is pre-formatted such that when it is printed and applied to an item, such as a paperback book, the “mail to” and “return address” information is on one side of the item, and a specialized or generic greeting or message is on the other side of the item. In addition, a postage application position is also indicated, as well as the postage amount, on the side with the “mail to” and “return address” information. FIG. 15 shows the mailing wrapper placed around a book. The edges of the wrapper are folded and taped, and the book is thereby made ready for mailing.

An additional document can be created onto which the system prints a more private message supplied by a member who is mailing an item to a recipient party. The second document may include instructions that indicate that it is to be placed inside the mailing wrapper document when applied to the item, such that the message created by the second member is not visible until the mailing wrapper is removed by the recipient party.

An automatic delivery confirmation feature will now be described. The US Postal Service (USPS) has a delivery feature that allows a user to obtain delivery confirmation that a package is successfully delivered to the recipient. The USPS assigns a tracking number to the package and prints a bar code or other machine-readable code on the package. When the postal carrier takes the item to the recipient's door or mailbox, he/she scans the package under a reader that reads the tracking number and associates that event with a successful delivery to the recipient.

Further, the system may, as an optional or basic feature, link with the USPS (e.g., the USPS web site) to obtain a tracking number and then include that tracking number and associated bar code or other machine-readable indicia in the mailing wrapper document that is emailed to the member who is going to send the item. The system will also assign a request identification number to the item (or items) that will be shipped with that wrapper. Thus, when the shipping member mails the package with the tracking number indicia exposed, the USPS carrier will scan that data when delivering the package to the recipient's door or mailbox. The USPS will then have confirmation of the package's delivery and will email or otherwise transmit confirmation of this event to the system. The system will receive the email and extract the tracking number data and match it with the corresponding request identification number. Thus, the system will automatically know when the item(s) corresponding to that request identification number is/are received. Upon this event, the system can apply a credit (or credits) to the member who shipped the items. With this feature, the recipient member or other party need not log into the system to confirm their recipient of the item.

The automatic confirmation feature can also be used to allow sender and recipient to track movement of the item between origin and destination using the association between the tracking number or identifier and the request identification number. While this feature has been described in connection with the USPS, it may also be used in a similar manner with other carriers, e.g., United Parcel Service (UPS) and Federal Express (FedEx).

The following is a further explanation of the credit management aspects of the swapping service. Generally, a typical trade involves only people. They trade item X for Y and the transaction is complete. In the context of the swapping service, if there are two people who both wanted to trade one item for another item, this would describe this system. However, the process that we have is more complicated.

Take the following example:

Users 1, 2 and 3 are all members or subscribers to the service. Person 4 is not a member. At their respective registration with the service, users 1, 2 and 3 each lists 3 books. Person 4 is not even aware of the service yet.

Users 1, 2, 3 are all registered with the service. If user 1 and 2 get together, they can trade item for item. However, for users to swap books in the system, credits must be issued so that there is a “sharing” of books that would allow for a 3-way trade (user 3). But how can they swap books for credit if none of them have credits to start the system? There needs to be a way of “starting” the credits, and the credits must be “backed up” with like-kind items.

A solution is to issue some number of credits up front so that the trading can begin. For example, the system issues an initial 3 credits each to users 1, 2 and 3. It is possible that the users will have used all items in the system, but each still has credits. The system has depleted itself of items, and the users of the system still expect to get more items. Therefore the system is altered to allow for more books to enter the system. Recognizing the shortfall of 3 books per user who enters the system, books are added back into the system to balance the credits initially issued.

The following example and economics apply. By charging an annual subscription or membership fee, the service is able to buy books to replenish the system and to ship them to the users. For example, a used paperback book will cost the service a minimum amount depending upon where it is purchased. For each user who is issued 3 credits to register with the system, the system must “replenish” itself with 3 books to avoid the problem outlined above. This will give each user at least 3 books to select from.

Additionally, the system will have to ship each of the books (at the then current book rate shipping cost from the United States Postal Service). The system also covers handling charges and hard costs (e.g. paper wrapper and tape) for those books. Therefore the total costs associated with the books the system buys and may ship includes the cost of the book, the postage and the handling and hard costs, which for purposes of income is deducted from the annual subscription fee revenue collected from each new user. Nevertheless, this solves the problem of having sufficient books in the system and initializing each new user with some credits.

It is possible that when user 1 ships a book to user 2, user 2 may claim that he/she did not receive it, whether he/she actually did or not. This creates a shortage in the system of one book. User 1 says that he/she shipped the book and will want the credit for doing so. User 2 wants the book. This situation may be caused by (a) user 1 never shipping the book, but saying he/she did ship it; (b) user 2 received it, but is denying it; or the delivery service lost the book in transit.

One solution to this scenario is to issue the credit expected by user 1 and to resend the same copy of the book requested by user 2 from another user who also has the same book. This now means that the system is short one extra book credit and the system must be replenished with one additional book. Now, the system must be replenished with the equivalent of 2 books.

User 2 in either situation is: (a) happy, because he/she finally got the book, or (b) user 2 has 2 copies of the same book. If the swapping service does not hear from user 2 again, then it may be assumed scenario (a) is true. If however, user 2 complains that he/she did not receive the book again from another user who had the same book, the service will contact user 2 and ask for an explanation. Customer Service may then decide whether to continue to support this user on or to kick them out of the system and refund part of their subscription fee (based on number of credits used and time in the system for the annual membership).

The system will also monitor user 1 to see if a pattern develops with that user claiming to have sent out a book and it not being received. If a pattern develops with user 1 not sending the book out more than once, then the system may determine whether this person should continue to be a member of the system.

When a book is not delivered, for any reason, then system may request another book from another member and still issue a credit for the original sender. This means that the service will have to cover the cost of replenishing a lost book and a lost credit. Further financial exposure is created.

Assume that the average person swaps 10 books per year. In reviewing the United States Postal Service's data on mail delivery, less than 1% of the U.S. mail is not delivered for some reason. Taking into account undelivered mail and add the dishonest people, then:

1 book lost by USPS—results in 1 book needing to be added back into the system.

2 books taken by dishonest members of the service—results in two more books added back into system. There is a financial impact of inserting one book into the system for each missing book through either loss or dishonesty. In the above scenario, a total of 3 books out of 100 books shipped must be added back into the system.

A total of 6 books out of 100 books shipped must be added back into the system.

Turning to FIGS. 16-19, a feature called “Wish List” will be described. If a member wants a book that is not active in the system at that given time, the member may add it to his/her Wish List and the system will notify that member when it becomes available, that is, when another member has listed it as being available for swapping. Likewise if a member sees a book on the Global Wish List (a list maintained by the system for books that members have entered into their personal Wish Lists) and a particular member has one of them in his/her collection but has not listed it, then that member can decide to list that book and be reasonably assured that someone will request it. It makes it more a “sure-swap”, and the member who ships that item will of course receive a credit when the Wish List member confirms receipt of the book.

First, with reference to FIGS. 16-18, the manner in which a member sets up his/her wish list will be described. FIG. 16 shows that a member can search for a book using the searching tools described above. The system will search to determine whether it is currently in the database and available from another member. If the book is in the database and is listed as being available from another member is, then the member will be given the option of requesting that book, as shown in FIG. 17. However, if the book is in the system's database, but is not listed as being available from another member, then the book can still be added to the member's Wish List as shown in FIG. 18. Thus, when the book is listed by another member, the member with it in his/her Wish List will be notified and given the option of requesting it. If that member who has that book on his/her Wish List no longer wants the book when it is eventually listed by another member, then that book will become part of the regular listing of available books. For example, a member may put the item on his/her wish list upon searching for it on the system and finding that it is not available, but after some period of time, that member may decide to find the book elsewhere but forget to delete it from his/her wish list. On the other hand, if the book is not in the system's database as being a book in print, then a screen such as the one shown in FIG. 19 may be displayed, indicating that the system database does not contain the book, but that the database is updated frequently and if a member lists it, it will certainly become available.

FIG. 20 illustrates the Global Wish List feature whereby the books in each member's Wish List is made available and searchable by all members. In this way, if a member has a book in his/her collection (but has not yet listed it) that is on the Global Wish List, he or she can list it and know that a credit will likely be secured by shipping it to the member with that book on his/her Wish List, if that member still wants it. If that member with who has that book on his/her Wish List no longer wants the book when it is eventually listed by another member, then that book will become part of the regular listing of available books. If that member who has that book on his/her Wish List no longer wants the book when it is eventually listed by another member, then that book will become part of the regular listing of available books.

Another Wish List related feature is to provide a separate wish list for items that a member may desire when the member does not have any credits to order it or does not otherwise want to put that item on his/her main Wish List. This secondary Wish List makes it more fair to other members that have available credits or otherwise have that item on their main Wish List so that those members have priority to that item once it is listed.

On a nightly basis, the system will review all of the Wish List data entered that day and notify members (via a web link, email, system message, etc.) so that members can look through their collections to see if they have an item that is on the latest Wish Lists.

Turning to FIGS. 21-23, the Save Search feature will be described. A user may frequently perform the same searches each time he/she signs onto the system. To save that user's effort, the system may save the search and send the member a nightly email notifying him/her if any new books for that search were posted in the last 24 hours, or some other time interval. Any time a user does a search, a particular icon may be displayed with those search results (as shown in FIGS. 21 and 22). When the user clicks or selects that icon, the system will prompt the user as shown in FIG. 22 to enter a name for the search, and then click the “Save Search” button. Then, as shown in FIG. 23, the user can tell the system, in his/her account preferences for “Saved Searches” whether to send an email daily for results that match that search. This allows the user to enter a search in one time, but lets the system do the work of running that search on a daily basis to alert the user of any items that match the search. For example, the system may conduct the search nightly and send an email the following morning. Any of the parameters that can be used in the search criteria can be saved as part of a saved search. These parameters are described above in connection with FIGS. 9 and 10.

FIG. 24 illustrates the Daily Digest feature. This feature allows a user to select genre or other more specific search parameters that the system performs on a daily (such as every evening) basis. The system will send a nightly email for just the genres selected in the Daily Digest genre parameters. The email includes all books posted into the system in the last 24 hours, for example, that fit that set of criteria. The user may configure the Daily Digest feature to perform the search and send an email on a desired basis, e.g., weekly, monthly, quarterly, etc., rather than a daily basis. Any or all of the parameters that are available for a search (described above in connection with FIGS. 9 and 10) can be used with the Daily Digest feature.

Turning to FIGS. 25 and 26, the Buddy List feature will be described. The Buddy List feature allows a member to create folders by topic, genre, author, etc., to associate with one or more other members. Messages can be sent, similar to email messages, between a first member and another member listed on the first member's Buddy List. This may be useful for members who share similar tastes in literature, etc. To this end, the first member will be allowed to see the books listed and contained in the Wish List for the other members on the first member's Buddy List, and visa versa. For example, FIG. 25 shows that a member created a Buddy List called Sports. In this Buddy List, the member may include the member profile name of any member he/she wishes to associate with Sports books. Whenever a particular icon, such as the one in Public Profile listing shown in FIG. 26, a member may select to add a member to his/her particular Buddy List to keep tabs on their current list of books and also their Wish List. You can even send them a personal message. The Buddy List feature may even tell a member when one of his/her “Buddies” are online with the system.

Turning to FIGS. 27-29, the Public Profiles feature will be described. The system maintains information on each member, including certain information concerning a member's usage of the system that is appropriate to share with any other member. For example, a member can see the titles of books a particular member has mailed to other members, and also the titles of books that particular member has ordered from other members. FIG. 27 shows, for a member, statistics concerning that member's usage of the system such as number of books ordered, number of books listed, etc., as shown. In addition, the system keeps track of where, in the U.S., a member has shipped books to other members as shown in FIG. 28, and also from where a particular member has received books from other members as shown in FIG. 29. When viewing the maps displaying books mailed from one member to another, a user can click on the dot which displays a pop-up graphic representing a particular member to see other books currently listed by that particular member.

Thus, for each member, a map may be displayed that shows all of the books are shipped from that member and geographically where that member received books from other members. In this screen a user may click on any source or destination member to send that member a message or see all of the books listed by that member, order one of those books or look at that member's wish list. Moreover, a member interested in that item may request to see a map that displays geographical locations of the members to which that particular item was shipped prior to shipment to the next member that requests the item or shipment to that interested member if he/she requests the item.

Related to the map feature is a book tracking feature. Each time a member posts a book that matches (by title) a book that he/she ordered from another member, the system stores data to track its path from one member to another member. In the course of tracking this information, the system may provide members along its path to share comments with other members in its path, exchange personal messages, conduct discussion forums etc., about that book.

Furthermore, the system may also maintain records of transactions conducted by members to keep track of which member or members (“Top Swappers)” have the most transactions with the service.

Still another feature is called the “Box-of-Books” swap feature. This allows members to ship books to each other for lower shipping cost per book, and without using their credits. Suppose member A has 30 books listed in his account and member B has 25 books in their list. In addition, suppose that members A and B are both willing to mail multiple books to each other to save on postage.

Member A searches member B's book list to select as many books as member A is willing to trade with member B. For example, member B has 10 books that member A would like. Member A may “prioritize” those books from 1 to 10 in the system (with 1 being the most important, and 10 being the least important).

The system sends an email invitation to the other member B asking him if he would like to trade up to 10 books with member A. Member B then logs onto the system and views the books listed by member A. Suppose that member B is interested only in 7 of member A's books. Member A mails those 7 books to member B, and member B mails the top 7 picked books to member A. Of course if member A still wants the remaining 3 books, he can use regular book credits to order them from member B. Then, member B will have the opportunity to request books from that member or other members using those 3 credits once the books are shipped member A.

The system may suggest that for bulk shipment, a member uses the U.S. Postal Service's (USPS) Media Mail service and have it certified or delivery confirmation at the Post Office so that the shipment is “protected”. In addition, the system will link to the USPS's tracking system to that a member received the bulk shipment. There is no need for a user to log into the system to record the receipt of the books.

The example below explains the savings that can be had when sending multiple books to one location (in bulk) instead of sending them one at a time (for USPS media mail rates as of the filing date of this application).

Number of Shipping Cost When Savings Compared to Books Mailed in Bulk Mailing Separately 1 $1.42 0 2 $1.84 + .55 = $2.39 54 cents (2 × $1.42 − $2.39) 3 $1.84 + .55 = $2.39 $1.87 (3 × $1.42 − 2.39) 4 $1.84 + .55 = $2.39 $3.29 (4 × $1.42 − 2.39) 5 $2.26 + .55 = $2.81 $4.29 (5 × $1.42 − 2.81) 6 $2.26 + .55 = $2.81 $5.71 (6 × $1.42 − 2.81) 7 $2.68 + .55 = $3.23 $6.71 (7 × $1.42 − 3.23) 8 $2.68 + .55 = $3.23 $8.13 (8 × $1.42 − 3.23) 9 $3.10 + .55 = $3.65 $9.13 (9 × $1.42 − 3.65) 10  $3.10 + .55 = $3.65 $10.55 (10 × $1.42 − 3.65)

Following this example, if a member mails 10 books together, the shipping cost per book is approximately 37 cents. This example assumes the following Media Mail Rates:

1 lb=$1.42; 2 lb=$1.84; 3 lb=$2.26; 4 lb=$2.68; 5 lb=$3.10 plus delivery confirmation of 55 cents.

It should be further understood that a user may order multiple books from the same member using credits and that member may ship the requested books in bulk to the ordering member. This will save postage as well, but credits were used for this transaction as in a typical transaction, unlike the “Box-of-Books” arrangement explained above.

To further promote the system, members may, at their option, receive software code from the service that they can insert in their emails to display a logo, URL, browser bookmarks, web site banner or other promotional identifying information, that is then displayed to non-members that receive emails from a member (outside of kthe system). In addition, the system may issue credit to members who refer new members to the service. The system may have a screen that allows a member to enter the email addresses for other people. The system will send a greeting and informational email to those email addresses, as well as reminder emails some period of time later if those people have not yet enrolled with the system. The system will keep track of which member supplied those email addresses so that when a person registers with the system using one of those supplied email address, the system can issue a credit to the corresponding member that supplied that email address.

The system may provide an “Away from Home” feature. If a member is traveling or otherwise unable to ship an item requested by another member, he/she may log in to the system before such time and configure the system to temporarily suspend his/her account. When a member requests the system to temporarily suspend his/her account, the system does not consider the items listed by the member as part of items available for swapping. When the member returns and/or deactivates this feature, the member's items are considered part of the database and available for swapping again. In addition, the member maintains his/her “position” with respect to a first-in first-out (FIFO) policy for items listed by that member (that are also listed by other members) prior to the temporary account deactivation.

Still another feature is a list called a “Books I've Read” list. The system may, for each member, track books that a member has ordered so that the user does not inadvertently order the same book again. One implementation of this feature is to automatically add a book to this list when a member requests or orders it from another member. Then, the next time the member requests or orders this same book, the system may display a prompt to the user to remind him/her that the book being requested matches one that the member had previously requested. The member can elect to bypass this reminder and order the book despite the reminder.

Swapping Tangible and Intangible Items Computer-Implemented System

FIG. 30 is a block diagram that illustrates a computer system 3000, upon which embodiments of the present teachings may be implemented. Computer system 3000 includes a bus 3002 or other communication mechanism for communicating information, and a processor 3004 coupled with bus 3002 for processing information. Computer system 3000 also includes a memory 3006, which can be a random access memory (RAM) or other dynamic storage device, coupled to bus 3002 for determining base calls, and instructions to be executed by processor 3004. Memory 3006 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 3004. Computer system 3000 further includes a read only memory (ROM) 3008 or other static storage device coupled to bus 3002 for storing static information and instructions for processor 3004. A storage device 3010, such as a magnetic disk or optical disk, is provided and coupled to bus 3002 for storing information and instructions.

Computer system 3000 may be coupled via bus 3002 to a display 3012, such as a cathode ray tube (CRT) or liquid crystal display (LCD), for displaying information to a computer user. An input device 3014, including alphanumeric and other keys, is coupled to bus 3002 for communicating information and command selections to processor 3004. Another type of user input device is cursor control 3016, such as a mouse, a trackball or cursor direction keys for communicating direction information and command selections to processor 3004 and for controlling cursor movement on display 3012. This input device typically has two degrees of freedom in two axes, a first axis (i.e., x) and a second axis (i.e., y), that allows the device to specify positions in a plane.

A computer system 3000 can perform the present teachings. Consistent with certain implementations of the present teachings, results are provided by computer system 3000 in response to processor 3004 executing one or more sequences of one or more instructions contained in memory 3006. Such instructions may be read into memory 3006 from another computer-readable medium, such as storage device 3010. Execution of the sequences of instructions contained in memory 3006 causes processor 3004 to perform the process described herein. Alternatively hard-wired circuitry may be used in place of or in combination with software instructions to implement the present teachings. Thus implementations of the present teachings are not limited to any specific combination of hardware circuitry and software.

The term “computer-readable medium” as used herein refers to any media that participates in providing instructions to processor 3004 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 3010. Volatile media includes dynamic memory, such as memory 3006. Transmission media includes coaxial cables, copper wire, and fiber optics, including the wires that comprise bus 3002.

Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punch cards, papertape, any other physical medium with patterns of holes, a RAM, PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, or any other tangible medium from which a computer can read.

Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to processor 3004 for execution. For example, the instructions may initially be carried on the magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 3000 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector coupled to bus 3002 can receive the data carried in the infra-red signal and place the data on bus 3002. Bus 3002 carries the data to memory 3006, from which processor 3004 retrieves and executes the instructions. The instructions received by memory 3006 may optionally be stored on storage device 3010 either before or after execution by processor 3004.

In accordance with various embodiments, instructions configured to be executed by a processor to perform a method are stored on a non-transitory and tangible computer-readable medium. The computer-readable medium can be a device that stores digital information. For example, a computer-readable medium includes a compact disc read-only memory (CD-ROM) as is known in the art for storing software. The computer-readable medium is accessed by a processor suitable for executing instructions configured to be executed.

The following descriptions of various implementations of the present teachings have been presented for purposes of illustration and description. It is not exhaustive and does not limit the present teachings to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practicing of the present teachings. Additionally, the described implementation includes software but the present teachings may be implemented as a combination of hardware and software or in hardware alone. The present teachings may be implemented with both object-oriented and non-object-oriented programming systems.

Systems and Methods of Data Processing

As described above, more and more like-kind tangible and intangible items are becoming available for swapping. As a result, systems and methods are needed to manage lending and swapping of tangible and intangible items.

In various embodiments, systems and methods are provided that manage a swap of tangible and intangible items among two or more users. These systems and methods use credits that represent a right to request a future swappable tangible or intangible item for the equivalent value of at least one previously swapped tangible or intangible item. Tangible items can include, but are not limited to, a book, a compact disc (CD), a lamp, a chair, or any tangible good. Intangible items can include, but are not limited to, digital files or a service. Digital files can include, but are not limited to, MP3 files or e-books.

In various embodiments, systems and methods manage the swap of tangible items for intangible items and intangible items for tangible items. The tangible items and intangible items are like-kind property, for example. In various embodiments, the tangible items and intangible items are not like-kind property.

FIG. 31 is a schematic diagram of a system 3100 for managing swaps of tangible and intangible items that shows the registration of a first tangible item 3151, in accordance with various embodiments. System includes network connection 3110, electronic database 3120, and server computer 3130. Server computer 3130 is connected to electronic database 3120 and communicates with user client devices through network connection 3110, for example. Network connection 3110 can be, but is not limited to, an Internet connection, a cellular phone network connection, or a short message service network (SMS) connection.

Server computer 3130 registers a first user 3141 in electronic database 3120. Server computer 3130 receives a first name of a first tangible item 3151 to list from first user device 3161 through network connection 3110. A client device can include, but is not limited to, a digital player, a mobile phone, a game player, a tablet computer, an e-book reader, or a computer. Server computer 3130 stores the first name in electronic database 3120 and lists the first name on a web site of server computer 3130.

FIG. 32 is a schematic diagram of a system 3200 for managing swaps of tangible and intangible items that shows the registration of a second intangible item 3252, in accordance with various embodiments. Server computer 3130 registers a second user 3242 in electronic database 3120. Server computer 3130 receives a second name of a second intangible item 3252 to list from second user device 3262 through network connection 3110. Server computer 3130 stores the second name in electronic database 3120 and lists the second name on a web site of server computer 3130.

FIG. 33 is a schematic diagram of a system 3300 for managing swaps of tangible and intangible items that shows the registration of a third tangible item 3353, in accordance with various embodiments. Server computer 3130 registers a third user 3343 in electronic database 3120. Server computer 3130 receives a third name of a third tangible item 3353 to list from third user device 3363 through network connection 3110. Server computer 3130 stores the third name in electronic database 3120 and lists the third name on a web site of server computer 3130.

FIG. 34 is a schematic diagram of a system 3400 for managing swaps of tangible and intangible items that shows a first request for second intangible item 3252, in accordance with various embodiments. Server computer 3130 receives a first request through network connection 3110 from first user device 3161 for second intangible item 3252 that begins a first transaction. Server computer 3130 removes a first credit from first user 3141 in electronic database 3120 that was stored for first user 3141 during a previous transaction.

FIG. 35 is a schematic diagram of a system 3500 for managing swaps of tangible and intangible items that shows a first message sent to second user device 3262, in accordance with various embodiments. Server computer 3130 sends a first message through network connection 3110 to second user device 3262 requesting that second intangible item 3252 be provided to first user 3141. An intangible item can be provided to a user by lending the intangible item to the user, sending the intangible item to the user, giving the user access to an account including the intangible item, giving access to digital player or reader, or providing a service for the user, for example. An intangible item can be provided for a finite amount of time, for example. In various embodiments, an intangible item can be provided for an infinite amount of time.

FIG. 36 is a schematic diagram of a system 3600 for managing swaps of tangible and intangible items that shows a second message sent from first user device 3161, in accordance with various embodiments. Server computer 3130 receives a second message through network connection 3110 confirming receipt of second intangible item 3252. Server computer 3130 stores a second credit for second user 3242 in electronic database 3120 to complete the first transaction.

FIG. 37 is a schematic diagram of a system 3700 for managing swaps of tangible and intangible items that shows a second request for third tangible item 3353, in accordance with various embodiments. Server computer 3130 receives a second request through network connection 3110 from second user device 3262 for third tangible item 3353 that begins a second transaction. Server computer 3130 removes the second credit from second user 3242 in electronic database 3120.

FIG. 38 is a schematic diagram of a system 3800 for managing swaps of tangible and intangible items that shows a third message sent to third user device 3363, in accordance with various embodiments. Server computer 3130 sends a third message through network connection 3110 to third user device 3363 requesting that third tangible item 3353 be provided to second user 3242. A tangible item can be provided to a user by shipping the item to the user, for example.

FIG. 39 is a schematic diagram of a system 3900 for managing swaps of tangible and intangible items that shows a forth message sent from second user device 3262, in accordance with various embodiments. Server computer 3130 receives a fourth message through network connection 3110 confirming receipt of third tangible item 3353. Server computer 3130 stores a third credit for third user 3343 in electronic database 3120 to complete the second transaction.

Server computer 3130 uses the first credit, the second credit, and the third credit to manage a swap of second intangible item 3252 and third tangible item 3353 among first user 3141, second user 3242, and third user 3343. The first credit, the second credit, and the third credit each represents a right to request a future swappable tangible or intangible item for the equivalent value of at least one previously swapped tangible or intangible item. In various embodiments, one or more credits are issued initially to a user so that the swapping process can begin.

As mentioned above, in various embodiments intangible items can include services. For example, one service that can be provided is an automobile ride home from a restaurant or a bar. A user can receive a credit for driving someone home. Then at some other time, they can use that credit to be driven home themselves. In various embodiments, services can be swapped that are not like-kind. For example, a trip home from a restaurant or a bar can be swapped for time spent holding a place in line. Further, in various embodiments a service can be swapped for another type of intangible item, like a digital file, or for a tangible item, such as a book.

Services can also include any professional or nonprofessional services. Professional services can include, but are not limited to, legal services, medical services, dental services, accounting services, or architectural services.

In various embodiments, a swapping system, such as system 3900 of FIG. 39, groups users 3141, 3242, and 3343 into a swapping group and items 3151, 3252, and 3353 are only shown to people in the swapping group. The use of swapping groups allows users to be more comfortable the tangible and intangibles they are requesting. For example, a user may be hesitant to swap a ride sharing service or a professional service with someone they do not know. If the service is offered from someone in a known swapping group, however, the user may be more willing to swap for that service. Similarly, a user may be hesitant to swap for a professional service from someone they do not know.

In various embodiments, a swapping system, such as system 3900, uses location information, such as global position satellite (GPS) information, to list items and to create swapping groups. For example, items 3151, 3252, and 3353 can be listed with the location provided from user devices 3161, 3261, and 3363. Further, server computer 3130 can create a swapping group based on the relative locations of users 3141, 3242, and 3343.

More generally an in various embodiments, a system, such as system 3900 is used for managing swaps of tangible and intangible items. Server computer 3130 registers a first user in electronic database 3120. Server computer 3130 receives a first name of a first tangible or intangible item to list from a first user device through network connection 3110. Server computer 3130 stores the first name in electronic database 3120, and lists the first name on a web site of server computer 3130.

Server computer 3130 registers a second user in electronic database 3120. Server computer 3130 receives a second name of a second tangible or intangible item to list from a second user device through network connection 3110. Server computer 3130 stores the second name in electronic database 3120, and lists the second name on the web site of server computer 3130.

Server computer 3130 registers a third user in electronic database 3120. Server computer 3130 receives a third name of a third tangible or intangible item to list from a third user device through network connection 3110. Server computer 3130 stores the third name in electronic database 3120, and lists the third name on the web site of the server computer.

Server computer 3130 receives a first request through network connection 3110 from the first user device for the second tangible or intangible item that begins a first transaction. Server computer 3130 removes a first credit from the first user in electronic database 3120 that was stored for the first user during a previous transaction. Server computer 3130 sends a first message through network connection 3110 to the second user device requesting that the second tangible or intangible item be provided to the first user. Server computer 3130 receives a second message through the network connection confirming receipt of the second tangible or intangible item. Server computer 3130 stores a second credit for the second user in electronic database 3120 to complete the first transaction.

Server computer 3130 receives a second request through network connection 3110 from the second user device for the third tangible or intangible item that begins a second transaction. Server computer 3130 removes the second credit from the second user in electronic database 3120. Server computer 3130 sends a third message through network connection 3110 to the third user device requesting that the third tangible or intangible item be provided to the second user. Server computer 3130 receives a fourth message through network connection 3110 confirming receipt of the third tangible or intangible item. Finally, server computer 3130 stores a third credit for the third user in the electronic database to complete the second transaction.

Server computer 3130 uses the first credit, the second credit, and the third credit to manage a swap of the second tangible or intangible item and the third tangible or intangible item among the first user, the second user, and the third user. The first credit, the second credit, and the third credit each represents a right to request a future swappable tangible or intangible item for the equivalent value of at least one previously swapped tangible or intangible item.

In various embodiments, the first tangible or intangible item, the second tangible or intangible item, or the third tangible or intangible item include a digital file. The digital file is, for example, an electronic book or eBook.

In various embodiments, the first tangible or intangible item, the second tangible or intangible item, or the third tangible or intangible item includes a service.

In various embodiments, the first user, the second user, and the third user are part of a swapping group and the first tangible or intangible item, the second tangible or intangible item, and the third tangible or intangible item are only shown to members of the swapping group.

In various embodiments, the first user device, the second user device, and the third user device provides location information. Server computer 3130 lists location information with the names of the first tangible or intangible item, the second tangible or intangible item, and the third tangible or intangible item on the web site. The location information of the first user device, the second user device, and the third user device is used to determine a swapping group, for example. In other words, only devices within a certain proximity of a location are allowed in a swapping group.

FIG. 40 is a flowchart showing a method 4000 for managing swaps of tangible and intangible items, in accordance with various embodiments.

In step 4010 of method 4000, a first user is registered in an electronic database. A first name of a first tangible or intangible item to list is received from a first user device through a network connection. The first name is stored in the electronic database. The first name is listed on a web site using a server computer.

In step 4020, a second user is registered in the electronic database. A second name of a second tangible or intangible item to list is received from a second user device through the network connection. The second name is stored in the electronic database. The second name is listed on the web site using the server computer.

In step 4030, a third user is registered in the electronic database. A third name of a third tangible or intangible item to list is received from a third user device through the network connection. The third name is stored in the electronic database. The third name is listed on the web site using the server computer.

In step 4040, a first request is received through the network connection from the first user device for the second tangible or intangible item that begins a first transaction. A first credit is removed from the first user in the electronic database that was stored for the first user during a previous transaction. A first message is sent through the network connection to the second user device requesting that the second tangible or intangible item be provided to the first user. A second message is received through the network connection confirming receipt of the second tangible or intangible item. A second credit for the second user is stored in the electronic database to complete the first transaction using the server computer.

In step 4050, a second request is received through the network connection from the second user device for the third tangible or intangible item that begins a second transaction. The second credit is removed from the second user in the electronic database. A third message is sent through the network connection to the third user device requesting that the third tangible or intangible item be provided to the second user. A fourth message is received through the network connection confirming receipt of the third tangible or intangible item. A third credit is stored for the third user in the electronic database to complete the second transaction using the server computer. The first credit, the second credit, and the third credit are used to manage a swap of the second tangible or intangible item and the third tangible or intangible item among the first user, the second user, and the third user. The first credit, the second credit, and the third credit each represents a right to request a future swappable tangible or intangible item for the equivalent value of at least one previously swapped tangible or intangible item.

In various embodiments, a computer program product includes a non-transitory and tangible computer-readable storage medium whose contents include a program which, when executed on a server computer, performs a method for managing swaps of tangible and intangible items. This method is performed by a system that includes one or more distinct software modules

FIG. 41 is a schematic diagram of a system 4100 that includes one or more distinct software modules that perform a method for managing swaps of tangible and intangible items, in accordance with various embodiments. System 4100 includes registration module 4110 and swapping module 4120.

Registration module 4110 registers a first user in an electronic database. Registration module 4110 receives a first name of a first tangible or intangible item to list from a first user device through a network connection. Registration module 4110 stores the first name in the electronic database. Registration module 4110 lists the first name on a web site.

Registration module 4110 registers a second user in the electronic database. Registration module 4110 receives a second name of a second tangible or intangible item to list from a second user device through the network connection. Registration module 4110 stores the second name in the electronic database. Registration module 4110 lists the second name on the web site.

Registration module 4110 registers a third user in the electronic database. Registration module 4110 receives a third name of a third tangible or intangible item to list from a third user device through the network connection. Registration module 4110 stores the third name in the electronic database. Registration module 4110 lists the third name on the web site.

Swapping module 4120 receives a first request through the network connection from the first user device for the second tangible or intangible item that begins a first transaction. Swapping module 4120 removes a first credit from the first user in the electronic database that was stored for the first user during a previous transaction. Swapping module 4120 sends a first message through the network connection to the second user device requesting that the second tangible or intangible item be provided to the first user. Swapping module 4120 receives a second message through the network connection confirming receipt of the second tangible or intangible item. Swapping module 4120 stores a second credit for the second user in the electronic database to complete the first transaction.

Swapping module 4120 receives a second request through the network connection from the second user device for the third tangible or intangible item that begins a second transaction. Swapping module 4120 removes the second credit from the second user in the electronic database. Swapping module 4120 sends a third message through the network connection to the third user device requesting that the third tangible or intangible item be provided to the second user. Swapping module 4120 receives a fourth message through the Internet connection confirming receipt of the third tangible or intangible item. Swapping module 4120 stores a third credit for the third user in the electronic database to complete the second transaction. The first credit, the second credit, and the third credit are used to manage a swap of the second tangible or intangible item and the third tangible or intangible item among the first user, the second user, and the third user. The first credit, the second credit, and the third credit each represents a right to request a future swappable tangible or intangible item for the equivalent value of at least one previously swapped tangible or intangible item.

While the present teachings are described in conjunction with various embodiments, it is not intended that the present teachings be limited to such embodiments. On the contrary, the present teachings encompass various alternatives, modifications, and equivalents, as will be appreciated by those of skill in the art.

Further, in describing various embodiments, the specification may have presented a method and/or process as a particular sequence of steps. However, to the extent that the method or process does not rely on the particular order of steps set forth herein, the method or process should not be limited to the particular sequence of steps described. As one of ordinary skill in the art would appreciate, other sequences of steps may be possible. Therefore, the particular order of the steps set forth in the specification should not be construed as limitations on the claims. In addition, the claims directed to the method and/or process should not be limited to the performance of their steps in the order written, and one skilled in the art can readily appreciate that the sequences may be varied and still remain within the spirit and scope of the various embodiments. 

What is claimed is:
 1. A system for managing swaps of intangible items, comprising: a server computer that is connected to an electronic database, and communicates with users through a network connection, wherein the server computer registers a first user in the electronic database, receives a first name of a first intangible item to list from a first user device through the network connection, stores the first name in the electronic database, and lists the first name on a web site of the server computer, wherein the server computer registers a second user in the electronic database, receives a second name of a second intangible item to list from a second user device through the network connection, stores the second name in the electronic database, and lists the second name on the web site of the server computer, wherein the server computer registers a third user in the electronic database, receives a third name of a third intangible item to list from a third user device through the network connection, stores the third name in the electronic database, and lists the third name on the web site of the server computer, wherein the server computer receives a first request through the network connection from the first user device for the second intangible item that begins a first transaction, removes a first credit from the first user in the electronic database that was stored for the first user during a previous transaction, sends a first message through the network connection to the second user device requesting that the second intangible item be provided to the first user, receives a second message through the network connection confirming receipt of the second intangible item, and stores a second credit for the second user in the electronic database to complete the first transaction, wherein the server computer receives a second request through the network connection from the second user device for the third intangible item that begins a second transaction, removes the second credit from the second user in the electronic database, sends a third message through the network connection to the third user device requesting that the third intangible item be provided to the second user, receives a fourth message through the network connection confirming receipt of the third intangible item, and stores a third credit for the third user in the electronic database to complete the second transaction, and wherein the server computer uses the first credit, the second credit, and the third credit to manage a swap of the second intangible item and the third intangible item among the first user, the second user, and the third user, wherein the first credit, the second credit, and the third credit each represents a right to request a future swappable intangible item for the equivalent value of at least one previously swapped intangible item.
 2. The system of claim 1, wherein the first intangible item, the second intangible item, or the third intangible item comprises a digital file.
 3. The system of claim 2, wherein the digital file comprises an electronic book.
 4. The system of claim 1, wherein the first intangible item, the second intangible item, or the third intangible item comprises a service.
 5. The system of claim 1, wherein the first user, the second user, and the third user are part of a swapping group and the first intangible item, the second intangible item, and the third intangible item are only shown to members of the swapping group.
 6. The system of claim 1, wherein the first user device, the second user device, and the third user device provides location information and the server computer lists location information with the names of the first intangible item, the second intangible item, and the third intangible item on the web site.
 7. The system of claim 6, wherein the location information of the first user device, the second user device, and the third user device is used to determine a swapping group.
 8. A method for managing swaps of intangible items, comprising: receiving a first name of a first intangible item to list from a first user device through a network connection, wherein a first user associated with the first user device is registered in an electronic database, and wherein the first name is stored in the electronic database and listed on a web site using a server computer, receiving a second name of a second intangible item to list from a second user device through the network connection, wherein a second user associated with the second user device is registered in the electronic database, and wherein the second name is stored in the electronic database and listed on the web site using the server computer, receiving a third name of a third intangible item to list from a third user device through the network connection, wherein a third user associated with the third user device is registered in the electronic database, and wherein the third name is stored in the electronic database and listed on the web site using the server computer, receiving a first request through the network connection from the first user device for the second intangible item that begins a first transaction, removing a first credit from the first user in the electronic database that was stored for the first user during a previous transaction, sending a first message through the network connection to the second user device requesting that the second intangible item be provided to the first user, receiving a second message through the network connection confirming receipt of the second intangible item, and storing a second credit for the second user in the electronic database to complete the first transaction using the server computer, and receiving a second request through the network connection from the second user device for the third intangible item that begins a second transaction, removing the second credit from the second user in the electronic database, sending a third message through the network connection to the third user device requesting that the third intangible item be provided to the second user, receiving a fourth message through the network connection confirming receipt of the third intangible item, and storing a third credit for the third user in the electronic database to complete the second transaction using the server computer, wherein the first credit, the second credit, and the third credit are used to manage a swap of the second intangible item and the third intangible item among the first user, the second user, and the third user and wherein the first credit, the second credit, and the third credit each represents a right to request a future swappable intangible item for the equivalent value of at least one previously swapped intangible item.
 9. The method of claim 8, wherein the first intangible item, the second intangible item, or the third intangible item comprises a digital file.
 10. The method of claim 9, wherein the digital file comprises an electronic book.
 11. The method of claim 8, wherein the first intangible item, the second intangible item, or the third intangible item comprises a service.
 12. The method of claim 8, wherein the first user, the second user, and the third user are part of a swapping group and the first intangible item, the second intangible item, and the third intangible item are only shown to members of the swapping group.
 13. The method of claim 8, wherein the first user device, the second user device, and the third user device provides location information and the server computer lists location information with the names of the first intangible item, the second intangible item, and the third intangible item on the web site.
 14. The method of claim 13, wherein the location information of the first user device, the second user device, and the third user device is used to determine a swapping group.
 15. A non-transitory computer-readable medium, whose contents include a program, which, when executed on a server computer, performs a method for managing swaps of intangible items, comprising: receiving a first name of a first intangible item to list from a first user device through a network connection, wherein a first user associated with the first user device is registered in an electronic database, and wherein the first name is stored in the electronic database and listed on a web site using a registration module, receiving a second name of a second intangible item to list from a second user device through the network connection, wherein a second user associated with the second user device is registered in the electronic database, and wherein the second name is stored in the electronic database and listed on the web site using the registration module, receiving a third name of a third intangible item to list from a third user device through the network connection, wherein a third user associated with the third user device is registered in the electronic database, and wherein the third name is stored in the electronic database and listed on the web site using the registration module, receiving a first request through the network connection from the first user device for the second intangible item that begins a first transaction, removing a first credit from the first user in the electronic database that was stored for the first user during a previous transaction, sending a first message through the network connection to the second user device requesting that the second intangible item be provided to the first user, receiving a second message through the network connection confirming receipt of the second intangible item, and storing a second credit for the second user in the electronic database to complete the first transaction using a swapping module, and receiving a second request through the network connection from the second user device for the third intangible item that begins a second transaction, removing the second credit from the second user in the electronic database, sending a third message through the network connection to the third user device requesting that the third intangible item be provided to the second user, receiving a fourth message through the network connection confirming receipt of the third intangible item, and storing a third credit for the third user in the electronic database to complete the second transaction using the swapping module, wherein the first credit, the second credit, and the third credit are used to manage a swap of the second intangible item and the third intangible item among the first user, the second user, and the third user and wherein the first credit, the second credit, and the third credit each represents a right to request a future swappable intangible item for the equivalent value of at least one previously swapped intangible item.
 16. The non-transitory computer-readable medium of claim 15, wherein the first intangible item, the second intangible item, or the third intangible item comprises a digital file.
 17. The non-transitory computer-readable medium of claim 16, wherein the digital file comprises an electronic book.
 18. The non-transitory computer-readable medium of claim 15, wherein the first intangible item, the second intangible item, or the third intangible item comprises a service.
 19. The non-transitory computer-readable medium of claim 15, wherein the first user, the second user, and the third user are part of a swapping group and the first intangible item, the second intangible item, and the third intangible item are only shown to members of the swapping group.
 20. The non-transitory computer-readable medium of claim 15, wherein the first user device, the second user device, and the third user device provides location information and the server computer lists location information with the names of the first intangible item, the second intangible item, and the third intangible item on the web site. 